Update model-libraries.ts for depthanything-ac #1650
Conversation
ghost233lism
requested review from
SBrandeis,
Wauplin,
gary149,
julien-c,
ngxson and
pcuenca
as code owners
There was a problem hiding this comment.
Hi @ghost233lism , thanks for your PR :) I've reviewed it and it's almost ready to merge. Can you make sure to add library_name: depthanything-ac to your model card metadata in https://huggingface.co/ghost233lism/DepthAnything-AC/blob/main/README.md? This will make it appear at https://huggingface.co/models?other=depthanything-ac for better discoverability.
| }, | ||
| "depthanything-ac": { | ||
| prettyLabel: "DepthAnything-AC", | ||
| repoName: "DepthAnythingAC", |
There was a problem hiding this comment.
| repoName: "DepthAnythingAC", | |
| repoName: "DepthAnything-AC", |
let's keep same as "prettyLabel"
| prettyLabel: "DepthAnything-AC", | ||
| repoName: "DepthAnythingAC", | ||
| repoUrl: "https://github.com/HVision-NKU/DepthAnythingAC", | ||
| snippets: snippets.DepthAnythingAC, |
There was a problem hiding this comment.
| snippets: snippets.DepthAnythingAC, |
snippet doesn't seem to be defined for that library
There was a problem hiding this comment.
If the model is fine-tuned from DepthAnything V2, then is it really necessary to add deptahanything-ac as a new library? If we assign library_name: depth-anything-v2, like here, would it just work out of the box? If so, I'd recommend doing that to reduce friction, and get usage snippets for free.
In addition, I'd recommend converting the model to transformers format and push it as a new repo. This way, it can be used directly from a transformers pipeline, which would also reduce friction and increase visibility. For example, the transformers version of depth-anything-v2 small had > 400K downloads in the last month, whereas downloads for the original library were ~10K.
3 participants
No description provided.